home *** CD-ROM | disk | FTP | other *** search
- Path: oxy.rust.net!usenet
- From: ebennett@rust.net
- Newsgroups: comp.lang.c++
- Subject: Re: bc4.0, Windows, Cursor
- Date: Sat, 20 Jan 1996 22:52:31 GMT
- Organization: Rust Net - High Speed Internet in Detroit 810-642-2276
- Message-ID: <4drh4q$1i2@oxy.rust.net>
- References: <4dpiba$gij@oxy.rust.net> <4dqink$sge@news1.usa.pipeline.com>
- NNTP-Posting-Host: liv-26.rust.net
- X-Newsreader: Forte Free Agent 1.0.82
-
- grantp@usa.pipeline.com(Pete) wrote:
-
- >Another (and often a better) way is to capture the mouse,
- >something like:
- >
- >WARNING Untested code using WinAPI -- OWL and MFC have
- >equivalent methods.
- >
- > ::SetCursor(hWnd, IDC_WAIT);
- > ::SetCapture(hWnd);
- > ..... do your stufffff
- > ::ReleaseCapture();
- >
- >
- >Of course, ReleaseCapture can be in a message response function
- >so that you can process other windows messages while the
- >hourglass remains in effect.
-
- Yes, I had forgotten about this. Thanks for the reminder.
-
- Of course, this has the downside that the mouse cursor is now always
- the busy cursor (until swiched back to the normal cursor) regardless
- of what window the cursor is actually over. This is sometimes
- desireable, and sometimes not. Depends on the application.
-
- Earl
-
-
-